Expect same controler GUID format for SDL2 on Windows as Linux#18635
Expect same controler GUID format for SDL2 on Windows as Linux#18635sonninnos merged 1 commit intolibretro:masterfrom
Conversation
|
I think this PR includes - by mistake probably - your own |
|
It sure does. Never run RA from the build dir. |
|
D'oh. You're right of course. That's why I shouldn't send PRs late at night.... Will fix this evening, apologies. |
|
I renamed the skeleton default cfg to avoid similar confusion in the future. Still weird how it got included in since Edit: Sigh, had to revert the rename because packaging scripts fail otherwise. |
|
Removed the Also tested a bit more locally with various different controllers (XInput, DInput, Switch controllers, wired & wireless, etc.), and this seems to have the desired effect for them all. Side note: Other than this small bug, I'm quite happy with the SDL controller experience overall. The usual XInput and DInput devices work the same as before, and some controllers that reported identical |
Description
RA parses the SDL joystick GUID differently for Windows than it does for Linux. However, SDL has used the same GUID format on all platforms for quite some time (since 2.0.5, and RA's currently bundling 2.0.14.0 with its Windows builds).
Since we currently parse the GUID wrong on Windows, without this change, using the SDL2 driver on Windows results in bogus
input_vendor_idandinput_product_idvalues:After this change, the values are correct:
(Notice the fixed
sdl2driver values now match the correct ones reported by thexinputdriver.)Related Issues
Fixes #18634.
Related Pull Requests
[Any other PRs from related repositories that might be needed for this pull request to work]